adTempus API
adTempus does not validate the structure or syntax of the extension definition file. Missing or incorrect information may cause errors, or may cause silent failures (such as an extension not being loaded). Always validate the extension file against the schema (XSD) file included with the extension API support files.
Some extension problems are reported directly to the user through error messages or job log messages. However, problems that occur during extension loading are only reported to the adTempus diagnostic logs.
By default, the logs will get written when a warning or error occurs. To confirm whether an extension is being loaded when no warnings or errors are reported, enable full diagnostic logging as discussed in the diagnostic logging article.
An extension may get loaded by three different adTempus processes.
The adTempus service loads all extensions definitions at startup. Any extension that is not correctly loaded by the service will not be available in the Console (even if it is registered on the Console computer) or for job execution.
The service does not attempt to load or validate any of the assemblies or types for the extension; it only loads the definition file. If there are problems with the definition or with the extension assembly, these will not be apparent until the extension is invoked in the Console or the by the host process during execution.
The adTempus Console loads all extension definitions at startup but does not validate them at this time. It loads the factory, settings, and user interface classes (if defined) as required. If any of these is misconfigured or problems occur, they are reported to the user, but it will generally be necessary to refer to the the diagnostic logs for troubleshooting.
The job host process (adtempus.jobhost.exe) loads the factory, settings, and executor classes for the extension when it is executed. If any of these is misconfigured or problems occur, they are reported to the user in the Job Log, but it will generally be necessary to refer to the the diagnostic logs for troubleshooting.